Mobile terminal

ABSTRACT

A mobile terminal includes: a display unit; a camera configured to acquire an image of a peripheral device; a short-range communication module configured to perform wireless communication with the peripheral device; and a controller configured to control the display unit, the camera, and the short-range communication module. The controller identifies the peripheral device based on at least one of a marker included in the acquired image of the peripheral device and a shape of the peripheral device, performs pairing with the identified peripheral device, and displays the image of the paired peripheral device and information on the paired peripheral device on the display unit.

CROSS-REFERENCE TO RELATED APPLICATIONS

Pursuant to 35 U.S.C. § 119(a), this application claims the benefit of earlier filing date and right of priority to Korean Patent Application No. 10-2016-0141594, filed on Oct. 28, 2016, the contents of which are hereby incorporated by reference herein in its entirety.

BACKGROUND

The present disclosure relates to a mobile terminal, and more particularly, to a mobile terminal which captures an image of a peripheral device, is connected to the peripheral device, and provides information on the connected peripheral device.

Terminals may be generally classified as mobile/portable terminals or stationary terminals according to their mobility. Mobile terminals may also be classified as handheld terminals or vehicle mounted terminals according to whether or not a user can directly carry the terminal.

Mobile terminals have become increasingly more functional. Examples of such functions include data and voice communications, capturing images and video via a camera, recording audio, playing music files via a speaker system, and displaying images and video on a display. Some mobile terminals include additional functionality which supports game playing, while other terminals are configured as multimedia players. More recently, mobile terminals have been configured to receive broadcast and multicast signals which permit viewing of content such as videos and television programs.

As such functions become more diversified, the mobile terminal can support more complicated functions such as capturing images or video, reproducing music or video files, playing games, receiving broadcast signals, and the like. By comprehensively and collectively implementing such functions, the mobile terminal may be embodied in the form of a multimedia player or device.

The mobile terminal may interwork with a peripheral device and provide information stored in the peripheral devices. To this end, an augmented reality method may be used.

However, in the past, in order to connect the peripheral device to the mobile terminal, it has been necessary for a user to perform a complicated process.

Furthermore, if the peripheral device capable of interworking with the mobile terminal does not include a display, there has been a limitation in that information on the peripheral device is not immediately confirmable.

SUMMARY

Accordingly, an object of the present disclosure is to address the above-noted and other problems.

Embodiments provide a mobile terminal which is pairable with a peripheral device only through a process of photographing the peripheral device.

Embodiments also provide a mobile terminal which provides information stored in a peripheral device not including a display or provides information for controlling an operation of the peripheral device.

In one embodiment, a mobile terminal includes: a display unit; a camera configured to acquire an image of a peripheral device; a short-range communication module configured to perform wireless communication with the peripheral device; and a controller configured to control the display unit, the camera, and the short-range communication module, wherein the controller identifies the peripheral device based on at least one of a marker included in the acquired image of the peripheral device and a shape of the peripheral device, performs pairing with the identified peripheral device, and displays the image of the paired peripheral device and information on the paired peripheral device on the display unit.

According to embodiments of the present disclosure, a mobile terminal may be connected to a peripheral device without a complicated process only through a process of photographing the peripheral device.

In addition, according to various embodiments of the present disclosure, a user may promptly and rapidly confirm information stored in a peripheral device not including a display or information for controlling an operation of the peripheral device on a mobile terminal.

Furthermore, according to various embodiments of the present disclosure, it is possible to provide great fun and a differentiated experience to the user by simplifying a difficult connection and a difficult management method of a peripheral device.

Further scope of applicability of the present disclosure will become apparent from the detailed description given hereinafter. However, it should be understood that the detailed description and specific examples, while indicating preferred embodiments of the invention, are given by illustration only, since various changes and modifications within the spirit and scope of the invention will become apparent to those skilled in the art from this detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram of a mobile terminal in accordance with the present disclosure.

FIGS. 1B and 1C are conceptual views of one example of the mobile terminal, viewed from different directions;

FIG. 2 is a conceptual view of a deformable mobile terminal according to an alternative embodiment of the present disclosure.

FIG. 3 is a conceptual view of a wearable mobile terminal according to another alternative embodiment of the present disclosure.

FIG. 4 is a conceptual view of a wearable mobile terminal according to another alternative embodiment of the present disclosure.

FIG. 5 is a ladder diagram illustrating an operating method between a mobile terminal and a peripheral device, according to an embodiment of the present disclosure.

FIGS. 6A and 6B are diagrams illustrating a process of capturing an image of a peripheral device and performing paring with the peripheral device, according to an embodiment of the present disclosure.

FIGS. 7 to 8 are diagrams illustrating a process of providing information on a peripheral device paired with a mobile terminal, according to an embodiment of the present disclosure.

FIG. 9 is a diagram illustrating an example of a change in a size of content stored in a peripheral device paired with a mobile terminal according to a distance between the peripheral device and the mobile terminal, according to an embodiment of the present disclosure.

FIG. 10 is a diagram illustrating an example in which content stored in a peripheral device displayed on a mobile terminal is stored in the mobile terminal if the content is selected, according to an embodiment of the present disclosure.

FIG. 11 is a diagram illustrating a process of controlling an operation of a peripheral device paired with a mobile terminal, according to an embodiment of the present disclosure.

FIGS. 12 and 13 are diagrams illustrating an example in which a mobile terminal captures an image of a peripheral device, is paired with the peripheral device, and provides information on the peripheral device in an augmented reality, according to another embodiment of the present disclosure.

FIG. 14 is a diagram illustrating an example in which a version of a peripheral device is recognized and information on the peripheral device corresponding to the recognized version is provided, according to an embodiment of the present disclosure.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Description will now be given in detail according to exemplary embodiments disclosed herein, with reference to the accompanying drawings. For the sake of brief description with reference to the drawings, the same or equivalent components may be provided with the same reference numbers, and description thereof will not be repeated. In general, a suffix such as “module” and “unit” may be used to refer to elements or components. Use of such a suffix herein is merely intended to facilitate description of the specification, and the suffix itself is not intended to give any special meaning or function. In the present disclosure, that which is well-known to one of ordinary skill in the relevant art has generally been omitted for the sake of brevity. The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any alterations, equivalents and substitutes in addition to those which are particularly set out in the accompanying drawings.

It will be understood that although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are generally only used to distinguish one element from another.

It will be understood that if an element is referred to as being “connected with” another element, the element can be connected with the other element or intervening elements may also be present. In contrast, if an element is referred to as being “directly connected with” another element, there are no intervening elements present.

A singular representation may include a plural representation unless it represents a definitely different meaning from the context. Terms such as “include” or “has” are used herein and should be understood that they are intended to indicate an existence of several components, functions or steps, disclosed in the specification, and it is also understood that greater or fewer components, functions, or steps may likewise be utilized.

Mobile terminals presented herein may be implemented using a variety of different types of terminals. Examples of such terminals include cellular phones, smart phones, user equipment, laptop computers, digital broadcast terminals, personal digital assistants (PDAs), portable multimedia players (PMPs), navigators, portable computers (PCs), slate PCs, tablet PCs, ultra books, wearable devices (for example, smart watches, smart glasses, head mounted displays (HMDs)), and the like.

By way of non-limiting example only, further description will be made with reference to particular types of mobile terminals. However, such teachings apply equally to other types of terminals, such as those types noted above. In addition, these teachings may also be applied to stationary terminals such as digital TV, desktop computers, and the like.

Reference is now made to FIGS. 1A-1C, where FIG. 1A is a block diagram of a mobile terminal in accordance with the present disclosure, and FIGS. 1B and 1C are conceptual views of one example of the mobile terminal, viewed from different directions.

The mobile terminal 100 is shown having components such as a wireless communication unit 110, an input unit 120, a sensing unit 140, an output unit 150, an interface unit 160, a memory 170, a controller 180, and a power supply unit 190. It is understood that implementing all of the illustrated components is not a requirement, and that greater or fewer components may alternatively be implemented.

Referring now to FIG. 1A, the mobile terminal 100 is shown having wireless communication unit 110 configured with several commonly implemented components. For instance, the wireless communication unit 110 typically includes one or more components which permit wireless communication between the mobile terminal 100 and a wireless communication system or network within which the mobile terminal is located.

The wireless communication unit 110 typically includes one or more modules which permit communications such as wireless communications between the mobile terminal 100 and a wireless communication system, communications between the mobile terminal 100 and another mobile terminal, communications between the mobile terminal 100 and an external server. Further, the wireless communication unit 110 typically includes one or more modules which connect the mobile terminal 100 to one or more networks. To facilitate such communications, the wireless communication unit 110 includes one or more of a broadcast receiving module 111, a mobile communication module 112, a wireless Internet module 113, a short-range communication module 114, and a location information module 115.

The input unit 120 includes a camera 121 for obtaining images or video, a microphone 122, which is one type of audio input device for inputting an audio signal, and a user input unit 123 (for example, a touch key, a push key, a mechanical key, a soft key, and the like) for allowing a user to input information. Data (for example, audio, video, image, and the like) is obtained by the input unit 120 and may be analyzed and processed by controller 180 according to device parameters, user commands, and combinations thereof.

The sensing unit 140 is typically implemented using one or more sensors configured to sense internal information of the mobile terminal, the surrounding environment of the mobile terminal, user information, and the like. For example, in FIG. 1A, the sensing unit 140 is shown having a proximity sensor 141 and an illumination sensor 142.

If desired, the sensing unit 140 may alternatively or additionally include other types of sensors or devices, such as a touch sensor, an acceleration sensor, a magnetic sensor, a G-sensor, a gyroscope sensor, a motion sensor, an RGB sensor, an infrared (IR) sensor, a finger scan sensor, a ultrasonic sensor, an optical sensor (for example, camera 121), a microphone 122, a battery gauge, an environment sensor (for example, a barometer, a hygrometer, a thermometer, a radiation detection sensor, a thermal sensor, and a gas sensor, among others), and a chemical sensor (for example, an electronic nose, a health care sensor, a biometric sensor, and the like), to name a few. The mobile terminal 100 may be configured to utilize information obtained from sensing unit 140, and in particular, information obtained from one or more sensors of the sensing unit 140, and combinations thereof.

The output unit 150 is typically configured to output various types of information, such as audio, video, tactile output, and the like. The output unit 150 is shown having a display unit 151, an audio output module 152, a haptic module 153, and an optical output module 154.

The display unit 151 may have an inter-layered structure or an integrated structure with a touch sensor in order to facilitate a touch screen. The touch screen may provide an output interface between the mobile terminal 100 and a user, as well as function as the user input unit 123 which provides an input interface between the mobile terminal 100 and the user.

The interface unit 160 serves as an interface with various types of external devices that can be coupled to the mobile terminal 100. The interface unit 160, for example, may include any of wired or wireless ports, external power supply ports, wired or wireless data ports, memory card ports, ports for connecting a device having an identification module, audio input/output (I/O) ports, video I/O ports, earphone ports, and the like. In some cases, the mobile terminal 100 may perform assorted control functions associated with a connected external device, in response to the external device being connected to the interface unit 160.

The memory 170 is typically implemented to store data to support various functions or features of the mobile terminal 100. For instance, the memory 170 may be configured to store application programs executed in the mobile terminal 100, data or instructions for operations of the mobile terminal 100, and the like. Some of these application programs may be downloaded from an external server via wireless communication. Other application programs may be installed within the mobile terminal 100 at time of manufacturing or shipping, which is typically the case for basic functions of the mobile terminal 100 (for example, receiving a call, placing a call, receiving a message, sending a message, and the like). It is common for application programs to be stored in the memory 170, installed in the mobile terminal 100, and executed by the controller 180 to perform an operation (or function) for the mobile terminal 100.

The controller 180 typically functions to control overall operation of the mobile terminal 100, in addition to the operations associated with the application programs. The controller 180 may provide or process information or functions appropriate for a user by processing signals, data, information and the like, which are input or output by the various components depicted in FIG. 1A, or activating application programs stored in the memory 170. As one example, the controller 180 controls some or all of the components illustrated in FIGS. 1A-1C according to the execution of an application program that have been stored in the memory 170.

The power supply unit 190 can be configured to receive external power or provide internal power in order to supply appropriate power required for operating elements and components included in the mobile terminal 100. The power supply unit 190 may include a battery, and the battery may be configured to be embedded in the terminal body, or configured to be detachable from the terminal body.

Referring still to FIG. 1A, various components depicted in this figure will now be described in more detail. Regarding the wireless communication unit 110, the broadcast receiving module 111 is typically configured to receive a broadcast signal and/or broadcast associated information from an external broadcast managing entity via a broadcast channel. The broadcast channel may include a satellite channel, a terrestrial channel, or both. In some embodiments, two or more broadcast receiving modules 111 may be utilized to facilitate simultaneously receiving of two or more broadcast channels, or to support switching among broadcast channels.

The broadcast managing entity may be a server which generates and transmits a broadcast signal and/or broadcast associated information, or a server which receives a pre-generated broadcast signal and/or broadcast associated information, and sends such items to the mobile terminal.

The broadcast signal may be implemented using any of a TV broadcast signal, a radio broadcast signal, a data broadcast signal, and combinations thereof, among others. The broadcast signal in some cases may further include a data broadcast signal combined with a TV or radio broadcast signal.

The broadcast signal may be encoded according to any of a variety of technical standards or broadcasting methods (for example, International Organization for Standardization (ISO), International Electrotechnical Commission (IEC), Digital Video Broadcast (DVB), Advanced Television Systems Committee (ATSC), and the like) for transmission and reception of digital broadcast signals. The broadcast receiving module 111 can receive the digital broadcast signals using a method appropriate for the transmission method utilized.

Examples of broadcast associated information may include information associated with a broadcast channel, a broadcast program, a broadcast event, a broadcast service provider, or the like. The broadcast associated information may also be provided via a mobile communication network, and in this case, received by the mobile communication module 112.

The broadcast associated information may be implemented in various formats. For instance, broadcast associated information may include an Electronic Program Guide (EPG) of Digital Multimedia Broadcasting (DMB), an Electronic Service Guide (ESG) of Digital Video Broadcast-Handheld (DVB-H), and the like. Broadcast signals and/or broadcast associated information received via the broadcast receiving module 111 may be stored in a suitable device, such as a memory 170.

The mobile communication module 112 can transmit and/or receive wireless signals to and from one or more network entities. Typical examples of a network entity include a base station, an external mobile terminal, a server, and the like. Such network entities form part of a mobile communication network, which is constructed according to technical standards or communication methods for mobile communications (for example, Global System for Mobile Communication (GSM), Code Division Multi Access (CDMA), CDMA2000 (Code Division Multi Access 2000), EV-DO (Enhanced Voice-Data Optimized or Enhanced Voice-Data Only), Wideband CDMA (WCDMA), High Speed Downlink Packet access (HSDPA), HSUPA (High Speed Uplink Packet Access), Long Term Evolution (LTE), LTE-A (Long Term Evolution-Advanced), and the like). Examples of wireless signals transmitted and/or received via the mobile communication module 112 include audio call signals, video (telephony) call signals, or various formats of data to support communication of text and multimedia messages.

The wireless Internet module 113 is configured to facilitate wireless Internet access. This module may be internally or externally coupled to the mobile terminal 100. The wireless Internet module 113 may transmit and/or receive wireless signals via communication networks according to wireless Internet technologies.

Examples of such wireless Internet access include Wireless LAN (WLAN), Wireless Fidelity (Wi-Fi), Wi-Fi Direct, Digital Living Network Alliance (DLNA), Wireless Broadband (WiBro), Worldwide Interoperability for Microwave Access (WiMAX), High Speed Downlink Packet Access (HSDPA), HSUPA (High Speed Uplink Packet Access), Long Term Evolution (LTE), LTE-A (Long Term Evolution-Advanced), and the like. The wireless Internet module 113 may transmit/receive data according to one or more of such wireless Internet technologies, and other Internet technologies as well.

In some embodiments, if the wireless Internet access is implemented according to, for example, WiBro, HSDPA, HSUPA, GSM, CDMA, WCDMA, LTE, LTE-A and the like, as part of a mobile communication network, the wireless Internet module 113 performs such wireless Internet access. As such, the wireless Internet module 113 may cooperate with, or function as, the mobile communication module 112.

The short-range communication module 114 is configured to facilitate short-range communications. Suitable technologies for implementing such short-range communications include BLUETOOTH™, Radio Frequency IDentification (RFID), Infrared Data Association (IrDA), Ultra-WideBand (UWB), ZigBee, Near Field Communication (NFC), Wireless-Fidelity (Wi-Fi), Wi-Fi Direct, Wireless USB (Wireless Universal Serial Bus), and the like. The short-range communication module 114 in general supports wireless communications between the mobile terminal 100 and a wireless communication system, communications between the mobile terminal 100 and another mobile terminal 100, or communications between the mobile terminal and a network where another mobile terminal 100 (or an external server) is located, via wireless area networks. One example of the wireless area networks is a wireless personal area networks.

In some embodiments, another mobile terminal (which may be configured similarly to mobile terminal 100) may be a wearable device, for example, a smart watch, a smart glass or a head mounted display (HMD), which is able to exchange data with the mobile terminal 100 (or otherwise cooperate with the mobile terminal 100). The short-range communication module 114 may sense or recognize the wearable device, and permit communication between the wearable device and the mobile terminal 100. In addition, if the sensed wearable device is a device which is authenticated to communicate with the mobile terminal 100, the controller 180, for example, may cause transmission of data processed in the mobile terminal 100 to the wearable device via the short-range communication module 114. Hence, a user of the wearable device may use the data processed in the mobile terminal 100 on the wearable device. For example, if a call is received in the mobile terminal 100, the user may answer the call using the wearable device. Also, if a message is received in the mobile terminal 100, the user can check the received message using the wearable device.

The location information module 115 is generally configured to detect, calculate, derive or otherwise identify a position of the mobile terminal. As an example, the location information module 115 includes a Global Position System (GPS) module, a Wi-Fi module, or both. If desired, the location information module 115 may alternatively or additionally function with any of the other modules of the wireless communication unit 110 to obtain data related to the position of the mobile terminal.

As one example, if the mobile terminal uses a GPS module, a position of the mobile terminal may be acquired using a signal sent from a GPS satellite. As another example, if the mobile terminal uses the Wi-Fi module, a position of the mobile terminal can be acquired based on information related to a wireless access point (AP) which transmits or receives a wireless signal to or from the Wi-Fi module.

The input unit 120 may be configured to permit various types of input to the mobile terminal 100. Examples of such input include audio, image, video, data, and user input. Image and video input is often obtained using one or more cameras 121. Such cameras 121 may process image frames of still pictures or video obtained by image sensors in a video or image capture mode. The processed image frames can be displayed on the display unit 151 or stored in memory 170. In some cases, the cameras 121 may be arranged in a matrix configuration to permit a plurality of images having various angles or focal points to be input to the mobile terminal 100. As another example, the cameras 121 may be located in a stereoscopic arrangement to acquire left and right images for implementing a stereoscopic image.

The microphone 122 is generally implemented to permit audio input to the mobile terminal 100. The audio input can be processed in various manners according to a function being executed in the mobile terminal 100. If desired, the microphone 122 may include assorted noise removing algorithms to remove unwanted noise generated in the course of receiving the external audio.

The user input unit 123 is a component that permits input by a user. Such user input may enable the controller 180 to control operation of the mobile terminal 100. The user input unit 123 may include one or more of a mechanical input element (for example, a key, a button located on a front and/or rear surface or a side surface of the mobile terminal 100, a dome switch, a jog wheel, a jog switch, and the like), or a touch-sensitive input, among others. As one example, the touch-sensitive input may be a virtual key or a soft key, which is displayed on a touch screen through software processing, or a touch key which is located on the mobile terminal at a location that is other than the touch screen. On the other hand, the virtual key or the visual key may be displayed on the touch screen in various shapes, for example, graphic, text, icon, video, or a combination thereof.

The sensing unit 140 is generally configured to sense one or more of internal information of the mobile terminal, surrounding environment information of the mobile terminal, user information, or the like. The controller 180 generally cooperates with the sensing unit 140 to control operation of the mobile terminal 100 or execute data processing, a function or an operation associated with an application program installed in the mobile terminal based on the sensing provided by the sensing unit 140. The sensing unit 140 may be implemented using any of a variety of sensors, some of which will now be described in more detail.

The proximity sensor 141 may include a sensor to sense presence or absence of an object approaching a surface, or an object located near a surface, by using an electromagnetic field, infrared rays, or the like without a mechanical contact. The proximity sensor 141 may be arranged at an inner region of the mobile terminal covered by the touch screen, or near the touch screen.

The proximity sensor 141, for example, may include any of a transmissive type photoelectric sensor, a direct reflective type photoelectric sensor, a mirror reflective type photoelectric sensor, a high-frequency oscillation proximity sensor, a capacitance type proximity sensor, a magnetic type proximity sensor, an infrared rays proximity sensor, and the like. If the touch screen is implemented as a capacitance type, the proximity sensor 141 can sense proximity of a pointer relative to the touch screen by changes of an electromagnetic field, which is responsive to an approach of an object with conductivity. In this case, the touch screen (touch sensor) may also be categorized as a proximity sensor.

The term “proximity touch” will often be referred to herein to denote the scenario in which a pointer is positioned to be proximate to the touch screen without contacting the touch screen. The term “contact touch” will often be referred to herein to denote the scenario in which a pointer makes physical contact with the touch screen. For the position corresponding to the proximity touch of the pointer relative to the touch screen, such position will correspond to a position where the pointer is perpendicular to the touch screen. The proximity sensor 141 may sense proximity touch, and proximity touch patterns (for example, distance, direction, speed, time, position, moving status, and the like).

In general, controller 180 processes data corresponding to proximity touches and proximity touch patterns sensed by the proximity sensor 141, and cause output of visual information on the touch screen. In addition, the controller 180 can control the mobile terminal 100 to execute different operations or process different data according to whether a touch with respect to a point on the touch screen is either a proximity touch or a contact touch.

A touch sensor can sense a touch applied to the touch screen, such as display unit 151, using any of a variety of touch methods. Examples of such touch methods include a resistive type, a capacitive type, an infrared type, and a magnetic field type, among others.

As one example, the touch sensor may be configured to convert changes of pressure applied to a specific part of the display unit 151, or convert capacitance occurring at a specific part of the display unit 151, into electric input signals. The touch sensor may also be configured to sense not only a touched position and a touched area, but also touch pressure and/or touch capacitance. A touch object is generally used to apply a touch input to the touch sensor. Examples of typical touch objects include a finger, a touch pen, a stylus pen, a pointer, or the like.

If a touch input is sensed by a touch sensor, corresponding signals may be transmitted to a touch controller. The touch controller may process the received signals, and then transmit corresponding data to the controller 180. Accordingly, the controller 180 may sense which region of the display unit 151 has been touched. Here, the touch controller may be a component separate from the controller 180, the controller 180, and combinations thereof.

In some embodiments, the controller 180 may execute the same or different controls according to a type of touch object that touches the touch screen or a touch key provided in addition to the touch screen. Whether to execute the same or different control according to the object which provides a touch input may be decided based on a current operating state of the mobile terminal 100 or a currently executed application program, for example.

The touch sensor and the proximity sensor may be implemented individually, or in combination, to sense various types of touches. Such touches includes a short (or tap) touch, a long touch, a multi-touch, a drag touch, a flick touch, a pinch-in touch, a pinch-out touch, a swipe touch, a hovering touch, and the like.

If desired, an ultrasonic sensor may be implemented to recognize position information relating to a touch object using ultrasonic waves. The controller 180, for example, may calculate a position of a wave generation source based on information sensed by an illumination sensor and a plurality of ultrasonic sensors. Since light is much faster than ultrasonic waves, the time for which the light reaches the optical sensor is much shorter than the time for which the ultrasonic wave reaches the ultrasonic sensor. The position of the wave generation source may be calculated using this fact. For instance, the position of the wave generation source may be calculated using the time difference from the time that the ultrasonic wave reaches the sensor based on the light as a reference signal.

The camera 121 typically includes at least one a camera sensor (CCD, CMOS etc.), a photo sensor (or image sensors), and a laser sensor.

Implementing the camera 121 with a laser sensor may allow detection of a touch of a physical object with respect to a 3D stereoscopic image. The photo sensor may be laminated on, or overlapped with, the display device. The photo sensor may be configured to scan movement of the physical object in proximity to the touch screen. In more detail, the photo sensor may include photo diodes and transistors at rows and columns to scan content received at the photo sensor using an electrical signal which changes according to the quantity of applied light. Namely, the photo sensor may calculate the coordinates of the physical object according to variation of light to thus obtain position information of the physical object.

The display unit 151 is generally configured to output information processed in the mobile terminal 100. For example, the display unit 151 may display execution screen information of an application program executing at the mobile terminal 100 or user interface (UI) and graphic user interface (GUI) information in response to the execution screen information.

In some embodiments, the display unit 151 may be implemented as a stereoscopic display unit for displaying stereoscopic images. A typical stereoscopic display unit may employ a stereoscopic display scheme such as a stereoscopic scheme (a glass scheme), an auto-stereoscopic scheme (glassless scheme), a projection scheme (holographic scheme), or the like.

In general, a 3D stereoscopic image may include a left image (e.g., a left eye image) and a right image (e.g., a right eye image). According to how left and right images are combined into a 3D stereoscopic image, a 3D stereoscopic imaging method can be divided into a top-down method in which left and right images are located up and down in a frame, an L-to-R (left-to-right or side by side) method in which left and right images are located left and right in a frame, a checker board method in which fragments of left and right images are located in a tile form, an interlaced method in which left and right images are alternately located by columns or rows, and a time sequential (or frame by frame) method in which left and right images are alternately displayed on a time basis.

Also, as for a 3D thumbnail image, a left image thumbnail and a right image thumbnail can be generated from a left image and a right image of an original image frame, respectively, and then combined to generate a single 3D thumbnail image. In general, the term “thumbnail” may be used to refer to a reduced image or a reduced still image. A generated left image thumbnail and right image thumbnail may be displayed with a horizontal distance difference there between by a depth corresponding to the disparity between the left image and the right image on the screen, thereby providing a stereoscopic space sense.

A left image and a right image required for implementing a 3D stereoscopic image may be displayed on the stereoscopic display unit using a stereoscopic processing unit. The stereoscopic processing unit can receive the 3D image and extract the left image and the right image, or can receive the 2D image and change it into a left image and a right image.

The audio output module 152 is generally configured to output audio data. Such audio data may be obtained from any of a number of different sources, such that the audio data may be received from the wireless communication unit 110 or may have been stored in the memory 170. The audio data may be output during modes such as a signal reception mode, a call mode, a record mode, a voice recognition mode, a broadcast reception mode, and the like. The audio output module 152 can provide audible output related to a particular function (e.g., a call signal reception sound, a message reception sound, etc.) performed by the mobile terminal 100. The audio output module 152 may also be implemented as a receiver, a speaker, a buzzer, or the like.

A haptic module 153 can be configured to generate various tactile effects that a user feels, perceive, or otherwise experience. A typical example of a tactile effect generated by the haptic module 153 is vibration. The strength, pattern and the like of the vibration generated by the haptic module 153 can be controlled by user selection or setting by the controller. For example, the haptic module 153 may output different vibrations in a combining manner or a sequential manner.

Besides vibration, the haptic module 153 can generate various other tactile effects, including an effect by stimulation such as a pin arrangement vertically moving to contact skin, a spray force or suction force of air through a jet orifice or a suction opening, a touch to the skin, a contact of an electrode, electrostatic force, an effect by reproducing the sense of cold and warmth using an element that can absorb or generate heat, and the like.

The haptic module 153 can also be implemented to allow the user to feel a tactile effect through a muscle sensation such as the user's fingers or arm, as well as transferring the tactile effect through direct contact. Two or more haptic modules 153 may be provided according to the particular configuration of the mobile terminal 100.

An optical output module 154 can output a signal for indicating an event generation using light of a light source. Examples of events generated in the mobile terminal 100 may include message reception, call signal reception, a missed call, an alarm, a schedule notice, an email reception, information reception through an application, and the like.

A signal output by the optical output module 154 may be implemented in such a manner that the mobile terminal emits monochromatic light or light with a plurality of colors. The signal output may be terminated as the mobile terminal senses that a user has checked the generated event, for example.

The interface unit 160 serves as an interface for external devices to be connected with the mobile terminal 100. For example, the interface unit 160 can receive data transmitted from an external device, receive power to transfer to elements and components within the mobile terminal 100, or transmit internal data of the mobile terminal 100 to such external device. The interface unit 160 may include wired or wireless headset ports, external power supply ports, wired or wireless data ports, memory card ports, ports for connecting a device having an identification module, audio input/output (I/O) ports, video I/O ports, earphone ports, or the like.

The identification module may be a chip that stores various information for authenticating authority of using the mobile terminal 100 and may include a user identity module (UIM), a subscriber identity module (SIM), a universal subscriber identity module (USIM), and the like. In addition, the device having the identification module (also referred to herein as an “identifying device”) may take the form of a smart card. Accordingly, the identifying device can be connected with the terminal 100 via the interface unit 160.

If the mobile terminal 100 is connected with an external cradle, the interface unit 160 can serve as a passage to allow power from the cradle to be supplied to the mobile terminal 100 or may serve as a passage to allow various command signals input by the user from the cradle to be transferred to the mobile terminal there through. Various command signals or power input from the cradle may operate as signals for recognizing that the mobile terminal is properly mounted on the cradle.

The memory 170 can store programs to support operations of the controller 180 and store input/output data (for example, phonebook, messages, still images, videos, etc.). The memory 170 may store data related to various patterns of vibrations and audio which are output in response to touch inputs on the touch screen.

The memory 170 may include one or more types of storage mediums including a Flash memory, a hard disk, a solid state disk, a silicon disk, a multimedia card micro type, a card-type memory (e.g., SD or DX memory, etc), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read-Only Memory (ROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Programmable Read-Only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. The mobile terminal 100 may also be operated in relation to a network storage device that performs the storage function of the memory 170 over a network, such as the Internet.

The controller 180 may typically control the general operations of the mobile terminal 100. For example, the controller 180 may set or release a lock state for restricting a user from inputting a control command with respect to applications if a status of the mobile terminal meets a preset condition.

The controller 180 can also perform the controlling and processing associated with voice calls, data communications, video calls, and the like, or perform pattern recognition processing to recognize a handwriting input or a picture drawing input performed on the touch screen as characters or images, respectively. In addition, the controller 180 can control one or a combination of those components in order to implement various exemplary embodiments disclosed herein.

The power supply unit 190 receives external power or provides internal power and supplies the appropriate power required for operating respective elements and components included in the mobile terminal 100. The power supply unit 190 may include a battery, which is typically rechargeable or be detachably coupled to the terminal body for charging.

The power supply unit 190 may include a connection port. The connection port may be configured as one example of the interface unit 160 to which an external charger for supplying power to recharge the battery is electrically connected.

As another example, the power supply unit 190 may be configured to recharge the battery in a wireless manner without use of the connection port. In this example, the power supply unit 190 can receive power, transferred from an external wireless power transmitter, using at least one of an inductive coupling method which is based on magnetic induction or a magnetic resonance coupling method which is based on electromagnetic resonance.

Various embodiments described herein may be implemented in a computer-readable medium, a machine-readable medium, or similar medium using, for example, software, hardware, or any combination thereof.

Referring now to FIGS. 1B and 1C, the mobile terminal 100 is described with reference to a bar-type terminal body. However, the mobile terminal 100 may alternatively be implemented in any of a variety of different configurations. Examples of such configurations include watch-type, clip-type, glasses-type, or as a folder-type, flip-type, slide-type, swing-type, and swivel-type in which two and more bodies are combined with each other in a relatively movable manner, and combinations thereof. Discussion herein will often relate to a particular type of mobile terminal (for example, bar-type, watch-type, glasses-type, and the like). However, such teachings with regard to a particular type of mobile terminal will generally apply to other types of mobile terminals as well.

The mobile terminal 100 will generally include a case (for example, frame, housing, cover, and the like) forming the appearance of the terminal. In this embodiment, the case is formed using a front case 101 and a rear case 102. Various electronic components are incorporated into a space formed between the front case 101 and the rear case 102. At least one middle case may be additionally positioned between the front case 101 and the rear case 102.

The display unit 151 is shown located on the front side of the terminal body to output information. As illustrated, a window 151 a of the display unit 151 may be mounted to the front case 101 to form the front surface of the terminal body together with the front case 101.

In some embodiments, electronic components may also be mounted to the rear case 102. Examples of such electronic components include a detachable battery 191, an identification module, a memory card, and the like. Rear cover 103 is shown covering the electronic components, and this cover may be detachably coupled to the rear case 102. Therefore, if the rear cover 103 is detached from the rear case 102, the electronic components mounted to the rear case 102 are externally exposed.

As illustrated, if the rear cover 103 is coupled to the rear case 102, a side surface of the rear case 102 is partially exposed. In some cases, upon the coupling, the rear case 102 may also be completely shielded by the rear cover 103. In some embodiments, the rear cover 103 may include an opening for externally exposing a camera 121 b or an audio output module 152 b.

The cases 101, 102, 103 may be formed by injection-molding synthetic resin or may be formed of a metal, for example, stainless steel (STS), aluminum (Al), titanium (Ti), or the like.

As an alternative to the example in which the plurality of cases form an inner space for accommodating components, the mobile terminal 100 may be configured such that one case forms the inner space. In this example, a mobile terminal 100 having a uni-body is formed in such a manner that synthetic resin or metal extends from a side surface to a rear surface.

If desired, the mobile terminal 100 may include a waterproofing unit (not shown) for preventing introduction of water into the terminal body. For example, the waterproofing unit may include a waterproofing member which is located between the window 151 a and the front case 101, between the front case 101 and the rear case 102, or between the rear case 102 and the rear cover 103, to hermetically seal an inner space if those cases are coupled.

The mobile terminal includes a display unit 151, first and second audio output modules 151 a/151 b, a proximity sensor 141, an illumination sensor 142, an optical output module 154, first and second cameras 121 a/121 b, first and second manipulation units 123 a/123 b, a microphone 122, interface unit 160 and the like.

It will be described for the mobile terminal as shown in FIGS. 1B and 1C. The display unit 151, the first audio output module 151 a, the proximity sensor 141, an illumination sensor 142, the optical output module 154, the first camera 121 a and the first manipulation unit 123 a are arranged in front surface of the terminal body, the second manipulation unit 123 b, the microphone 122 and interface unit 160 are arranged in side surface of the terminal body, and the second audio output modules 151 b and the second camera 121 b are arranged in rear surface of the terminal body.

However, it is to be understood that alternative arrangements are possible and within the teachings of the instant disclosure. Some components may be omitted or rearranged. For example, the first manipulation unit 123 a may be located on another surface of the terminal body, and the second audio output module 152 b may be located on the side surface of the terminal body.

The display unit 151 outputs information processed in the mobile terminal 100. The display unit 151 may be implemented using one or more suitable display devices. Examples of such suitable display devices include a liquid crystal display (LCD), a thin film transistor-liquid crystal display (TFT-LCD), an organic light emitting diode (OLED), a flexible display, a 3-dimensional (3D) display, an e-ink display, and combinations thereof.

The display unit 151 may be implemented using two display devices, which can implement the same or different display technology. For instance, a plurality of the display units 151 may be arranged on one side, either spaced apart from each other, or these devices may be integrated, or these devices may be arranged on different surfaces.

The display unit 151 may also include a touch sensor which senses a touch input received at the display unit. If a touch is input to the display unit 151, the touch sensor may be configured to sense this touch and the controller 180, for example, may generate a control command or other signal corresponding to the touch. The content which is input in the touching manner may be a text or numerical value, or a menu item which can be indicated or designated in various modes.

The touch sensor may be configured in a form of a film having a touch pattern, disposed between the window 151 a and a display on a rear surface of the window 151 a, or a metal wire which is patterned directly on the rear surface of the window 151 a. Alternatively, the touch sensor may be integrally formed with the display. For example, the touch sensor may be disposed on a substrate of the display or within the display.

The display unit 151 may also form a touch screen together with the touch sensor. Here, the touch screen may serve as the user input unit 123 (see FIG. 1A). Therefore, the touch screen may replace at least some of the functions of the first manipulation unit 123 a.

The first audio output module 152 a may be implemented in the form of a speaker to output voice audio, alarm sounds, multimedia audio reproduction, and the like.

The window 151 a of the display unit 151 will typically include an aperture to permit audio generated by the first audio output module 152 a to pass. One alternative is to allow audio to be released along an assembly gap between the structural bodies (for example, a gap between the window 151 a and the front case 101). In this case, a hole independently formed to output audio sounds may not be seen or is otherwise hidden in terms of appearance, thereby further simplifying the appearance and manufacturing of the mobile terminal 100.

The optical output module 154 can be configured to output light for indicating an event generation. Examples of such events include a message reception, a call signal reception, a missed call, an alarm, a schedule notice, an email reception, information reception through an application, and the like. If a user has checked a generated event, the controller can control the optical output unit 154 to stop the light output.

The first camera 121 a can process image frames such as still or moving images obtained by the image sensor in a capture mode or a video call mode. The processed image frames can then be displayed on the display unit 151 or stored in the memory 170.

The first and second manipulation units 123 a and 123 b are examples of the user input unit 123, which may be manipulated by a user to provide input to the mobile terminal 100. The first and second manipulation units 123 a and 123 b may also be commonly referred to as a manipulating portion, and may employ any tactile method that allows the user to perform manipulation such as touch, push, scroll, or the like. The first and second manipulation units 123 a and 123 b may also employ any non-tactile method that allows the user to perform manipulation such as proximity touch, hovering, or the like.

FIG. 1B illustrates the first manipulation unit 123 a as a touch key, but possible alternatives include a mechanical key, a push key, a touch key, and combinations thereof.

Input received at the first and second manipulation units 123 a and 123 b may be used in various ways. For example, the first manipulation unit 123 a may be used by the user to provide an input to a menu, home key, cancel, search, or the like, and the second manipulation unit 123 b may be used by the user to provide an input to control a volume level being output from the first or second audio output modules 152 a or 152 b, to switch to a touch recognition mode of the display unit 151, or the like.

As another example of the user input unit 123, a rear input unit (not shown) may be located on the rear surface of the terminal body. The rear input unit can be manipulated by a user to provide input to the mobile terminal 100. The input may be used in a variety of different ways. For example, the rear input unit may be used by the user to provide an input for power on/off, start, end, scroll, control volume level being output from the first or second audio output modules 152 a or 152 b, switch to a touch recognition mode of the display unit 151, and the like. The rear input unit may be configured to permit touch input, a push input, or combinations thereof.

The rear input unit may be located to overlap the display unit 151 of the front side in a thickness direction of the terminal body. As one example, the rear input unit may be located on an upper end portion of the rear side of the terminal body such that a user can easily manipulate it using a forefinger if the user grabs the terminal body with one hand. Alternatively, the rear input unit can be positioned at most any location of the rear side of the terminal body.

Embodiments that include the rear input unit may implement some or all of the functionality of the first manipulation unit 123 a in the rear input unit. As such, in situations where the first manipulation unit 123 a is omitted from the front side, the display unit 151 can have a larger screen.

As a further alternative, the mobile terminal 100 may include a finger scan sensor which scans a user's fingerprint. The controller 180 can then use fingerprint information sensed by the finger scan sensor as part of an authentication procedure. The finger scan sensor may also be installed in the display unit 151 or implemented in the user input unit 123.

The microphone 122 is shown located at an end of the mobile terminal 100, but other locations are possible. If desired, multiple microphones may be implemented, with such an arrangement permitting the receiving of stereo sounds.

The interface unit 160 may serve as a path allowing the mobile terminal 100 to interface with external devices. For example, the interface unit 160 may include one or more of a connection terminal for connecting to another device (for example, an earphone, an external speaker, or the like), a port for near field communication (for example, an Infrared Data Association (IrDA) port, a Bluetooth port, a wireless LAN port, and the like), or a power supply terminal for supplying power to the mobile terminal 100. The interface unit 160 may be implemented in the form of a socket for accommodating an external card, such as Subscriber Identification Module (SIM), User Identity Module (UIM), or a memory card for information storage.

The second camera 121 b is shown located at the rear side of the terminal body and includes an image capturing direction that is substantially opposite to the image capturing direction of the first camera 121 a. If desired, second camera 121 b may alternatively be located at other locations, or made to be moveable, in order to have a different image capturing direction from that which is shown.

The second camera 121 b can include a plurality of lenses arranged along at least one line. The plurality of lenses may also be arranged in a matrix configuration. The cameras may be referred to as an “array camera.” If the second camera 121 b is implemented as an array camera, images may be captured in various manners using the plurality of lenses and images with better qualities.

As shown in FIG. 1C, a flash 124 is shown adjacent to the second camera 121 b. If an image of a subject is captured with the camera 121 b, the flash 124 may illuminate the subject.

As shown in FIG. 1B, the second audio output module 152 b can be located on the terminal body. The second audio output module 152 b may implement stereophonic sound functions in conjunction with the first audio output module 152 a, and may be also used for implementing a speaker phone mode for call communication.

At least one antenna for wireless communication may be located on the terminal body. The antenna may be installed in the terminal body or formed by the case. For example, an antenna which configures a part of the broadcast receiving module 111 may be retractable into the terminal body. Alternatively, an antenna may be formed using a film attached to an inner surface of the rear cover 103, or a case that includes a conductive material.

A power supply unit 190 for supplying power to the mobile terminal 100 may include a battery 191, which is mounted in the terminal body or detachably coupled to an outside of the terminal body. The battery 191 may receive power via a power source cable connected to the interface unit 160. Also, the battery 191 can be recharged in a wireless manner using a wireless charger. Wireless charging may be implemented by magnetic induction or electromagnetic resonance.

The rear cover 103 is shown coupled to the rear case 102 for shielding the battery 191, to prevent separation of the battery 191, and to protect the battery 191 from an external impact or from foreign material. If the battery 191 is detachable from the terminal body, the rear case 103 may be detachably coupled to the rear case 102.

An accessory for protecting an appearance or assisting or extending the functions of the mobile terminal 100 can also be provided on the mobile terminal 100. As one example of an accessory, a cover or pouch for covering or accommodating at least one surface of the mobile terminal 100 may be provided. The cover or pouch may cooperate with the display unit 151 to extend the function of the mobile terminal 100. Another example of the accessory is a touch pen for assisting or extending a touch input to a touch screen.

FIG. 2 is a conceptual view of a deformable mobile terminal according to an alternative embodiment of the present disclosure. In this figure, mobile terminal 200 is shown having display unit 251, which is a type of display that is deformable by an external force. This deformation, which includes display unit 251 and other components of mobile terminal 200, may include any of curving, bending, folding, twisting, rolling, and combinations thereof. The deformable display unit 251 may also be referred to as a “flexible display unit.” In some implementations, the flexible display unit 251 may include a general flexible display, electronic paper (also known as e-paper), and combinations thereof. In general, mobile terminal 200 may be configured to include features that are the same or similar to that of mobile terminal 100 of FIGS. 1A to 1C.

The flexible display of mobile terminal 200 is generally formed as a lightweight, non-fragile display, which still exhibits characteristics of a conventional flat panel display, but is instead fabricated on a flexible substrate which can be deformed as noted previously.

The term e-paper may be used to refer to a display technology employing the characteristic of a general ink, and is different from the conventional flat panel display in view of using reflected light. E-paper is generally understood as changing displayed information using a twist ball or via electrophoresis using a capsule.

If in a state that the flexible display unit 251 is not deformed (for example, in a state with an infinite radius of curvature and referred to as a first state), a display region of the flexible display unit 251 includes a generally flat surface. If in a state that the flexible display unit 251 is deformed from the first state by an external force (for example, a state with a finite radius of curvature and referred to as a second state), the display region may become a curved surface or a bent surface. As illustrated, information displayed in the second state may be visual information output on the curved surface. The visual information may be realized in such a manner that a light emission of each unit pixel (sub-pixel) arranged in a matrix configuration is controlled independently. The unit pixel denotes an elementary unit for representing one color.

According to one alternative embodiment, the first state of the flexible display unit 251 may be a curved state (for example, a state of being curved from up to down or from right to left), instead of being in flat state. In this embodiment, if an external force is applied to the flexible display unit 251, the flexible display unit 251 may transition to the second state such that the flexible display unit is deformed into the flat state (or a less curved state) or into a more curved state.

If desired, the flexible display unit 251 may implement a flexible touch screen using a touch sensor in combination with the display. If a touch is received at the flexible touch screen, the controller 180 can execute certain control corresponding to the touch input. In general, the flexible touch screen is configured to sense touch and other input while in both the first and second states.

One option is to configure the mobile terminal 200 to include a deformation sensor which senses the deforming of the flexible display unit 251. The deformation sensor may be included in the sensing unit 140.

The deformation sensor may be located in the flexible display unit 251 or the case 201 to sense information related to the deforming of the flexible display unit 251. Examples of such information related to the deforming of the flexible display unit 251 may be a deformed direction, a deformed degree, a deformed position, a deformed amount of time, an acceleration that the deformed flexible display unit 251 is restored, and the like. Other possibilities include most any type of information which can be sensed in response to the curving of the flexible display unit or sensed while the flexible display unit 251 is transitioning into, or existing in, the first and second states.

In some embodiments, controller 180 or other component can change information displayed on the flexible display unit 251, or generate a control signal for controlling a function of the mobile terminal 200, based on the information related to the deforming of the flexible display unit 251. Such information is typically sensed by the deformation sensor.

The mobile terminal 200 is shown having a case 201 for accommodating the flexible display unit 251. The case 201 can be deformable together with the flexible display unit 251, taking into account the characteristics of the flexible display unit 251.

A battery (not shown in this figure) located in the mobile terminal 200 may also be deformable in cooperation with the flexible display unit 261, taking into account the characteristic of the flexible display unit 251. One technique to implement such a battery is to use a stack and folding method of stacking battery cells.

The deformation of the flexible display unit 251 not limited to perform by an external force. For example, the flexible display unit 251 can be deformed into the second state from the first state by a user command, application command, or the like.

In accordance with still further embodiments, a mobile terminal may be configured as a device which is wearable on a human body. Such devices go beyond the usual technique of a user grasping the mobile terminal using their hand. Examples of the wearable device include a smart watch, a smart glass, a head mounted display (HMD), and the like.

A typical wearable device can exchange data with (or cooperate with) another mobile terminal 100. In such a device, the wearable device generally has functionality that is less than the cooperating mobile terminal. For instance, the short-range communication module 114 of a mobile terminal 100 may sense or recognize a wearable device that is near-enough to communicate with the mobile terminal. In addition, if the sensed wearable device is a device which is authenticated to communicate with the mobile terminal 100, the controller 180 may transmit data processed in the mobile terminal 100 to the wearable device via the short-range communication module 114, for example. Hence, a user of the wearable device can use the data processed in the mobile terminal 100 on the wearable device. For example, if a call is received in the mobile terminal 100, the user can answer the call using the wearable device. Also, if a message is received in the mobile terminal 100, the user can check the received message using the wearable device.

FIG. 3 is a perspective view illustrating one example of a watch-type mobile terminal 300 in accordance with another exemplary embodiment. As illustrated in FIG. 3, the watch-type mobile terminal 300 includes a main body 301 with a display unit 351 and a band 302 connected to the main body 301 to be wearable on a wrist. In general, mobile terminal 300 may be configured to include features that are the same or similar to that of mobile terminal 100 of FIGS. 1A to 1C.

The main body 301 may include a case having a certain appearance. As illustrated, the case may include a first case 301 a and a second case 301 b cooperatively defining an inner space for accommodating various electronic components. Other configurations are possible. For instance, a single case may alternatively be implemented, with such a case being configured to define the inner space, thereby implementing a mobile terminal 300 with a uni-body.

The watch-type mobile terminal 300 can perform wireless communication, and an antenna for the wireless communication can be installed in the main body 301. The antenna may extend its function using the case. For example, a case including a conductive material may be electrically connected to the antenna to extend a ground area or a radiation area.

The display unit 351 is shown located at the front side of the main body 301 so that displayed information is viewable to a user. In some embodiments, the display unit 351 includes a touch sensor so that the display unit can function as a touch screen. As illustrated, window 351 a is positioned on the first case 301 a to form a front surface of the terminal body together with the first case 301 a.

The illustrated embodiment includes audio output module 352, a camera 321, a microphone 322, and a user input unit 323 positioned on the main body 301. If the display unit 351 is implemented as a touch screen, additional function keys may be minimized or eliminated. For example, if the touch screen is implemented, the user input unit 323 may be omitted.

The band 302 is commonly worn on the user's wrist and may be made of a flexible material for facilitating wearing of the device. As one example, the band 302 may be made of fur, rubber, silicon, synthetic resin, or the like. The band 302 may also be configured to be detachable from the main body 301. Accordingly, the band 302 may be replaceable with various types of bands according to a user's preference.

In one configuration, the band 302 may be used for extending the performance of the antenna. For example, the band may include therein a ground extending portion (not shown) electrically connected to the antenna to extend a ground area.

The band 302 may include fastener 302 a. The fastener 302 a may be implemented into a buckle type, a snap-fit hook structure, a Velcro® type, or the like, and include a flexible section or material. The drawing illustrates an example that the fastener 302 a is implemented using a buckle.

FIG. 4 is a perspective view illustrating one example of a glass-type mobile terminal 400 according to another exemplary embodiment. The glass-type mobile terminal 400 can be wearable on a head of a human body and provided with a frame (case, housing, etc.) therefor. The frame may be made of a flexible material to be easily worn. The frame of mobile terminal 400 is shown having a first frame 401 and a second frame 402, which can be made of the same or different materials. In general, mobile terminal 400 may be configured to include features that are the same or similar to that of mobile terminal 100 of FIGS. 1A-1C.

The frame may be supported on the head and defines a space for mounting various components. As illustrated, electronic components, such as a control module 480, an audio output module 452, and the like, may be mounted to the frame part. Also, a lens 403 for covering either or both of the left and right eyes may be detachably coupled to the frame part.

The control module 480 controls various electronic components disposed in the mobile terminal 400. The control module 480 may be understood as a component corresponding to the aforementioned controller 180. FIG. 4 illustrates that the control module 480 is installed in the frame part on one side of the head, but other locations are possible.

The display unit 451 may be implemented as a head mounted display (HMD). The HMD refers to display techniques by which a display is mounted to a head to show an image directly in front of a user's eyes. In order to provide an image directly in front of the user's eyes if the user wears the glass-type mobile terminal 400, the display unit 451 may be located to correspond to either or both of the left and right eyes. FIG. 4 illustrates that the display unit 451 is located on a portion corresponding to the right eye to output an image viewable by the user's right eye.

The display unit 451 may project an image into the user's eye using a prism. Also, the prism may be formed from optically transparent material such that the user can view both the projected image and a general visual field (a range that the user views through the eyes) in front of the user.

In such a manner, the image output through the display unit 451 may be viewed while overlapping with the general visual field. The mobile terminal 400 may provide an augmented reality (AR) by overlaying a virtual image on a realistic image or background using the display.

The camera 421 may be located adjacent to either or both of the left and right eyes to capture an image. Since the camera 421 is located adjacent to the eye, the camera 421 can acquire a scene that the user is currently viewing. The camera 421 may be positioned at most any location of the mobile terminal. In some embodiments, multiple cameras 421 may be utilized. Such multiple cameras 421 may be used to acquire a stereoscopic image.

The glass-type mobile terminal 400 may include user input units 423 a and 423 b, which can each be manipulated by the user to provide an input. The user input units 423 a and 423 b may employ techniques which permit input via a tactile input. Typical tactile inputs include a touch, push, or the like. The user input units 423 a and 423 b are shown operable in a pushing manner and a touching manner as they are located on the frame part and the control module 480, respectively.

If desired, mobile terminal 400 may include a microphone which processes input sound into electric audio data, and an audio output module 452 for outputting audio. The audio output module 452 may be configured to produce audio in a general audio output manner or an osteoconductive manner. If the audio output module 452 is implemented in the osteoconductive manner, the audio output module 452 may be closely adhered to the head if the user wears the mobile terminal 400 and vibrate the user's skull to transfer sounds.

A communication system which is operable with the variously described mobile terminals will now be described in more detail. Such a communication system may be configured to utilize any of a variety of different air interfaces and/or physical layers. Examples of such air interfaces utilized by the communication system include Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Universal Mobile Telecommunications System (UMTS) (including, Long Term Evolution (LTE), LTE-A (Long Term Evolution-Advanced)), Global System for Mobile Communications (GSM), and the like.

By way of a non-limiting example only, further description will relate to a CDMA communication system, but such teachings apply equally to other system types including a CDMA wireless communication system as well as OFDM (Orthogonal Frequency Division Multiplexing) wireless communication system. A CDMA wireless communication system generally includes one or more mobile terminals (MT or User Equipment, UE) 100, one or more base stations (BSs, NodeB, or evolved NodeB), one or more base station controllers (BSCs), and a mobile switching center (MSC). The MSC is configured to interface with a conventional Public Switched Telephone Network (PSTN) and the BSCs. The BSCs are coupled to the base stations via backhaul lines. The backhaul lines may be configured in accordance with any of several known interfaces including, for example, E1/T1, ATM, IP, PPP, Frame Relay, HDSL, ADSL, or xDSL. Hence, the plurality of BSCs can be included in the CDMA wireless communication system.

Each base station may include one or more sectors, each sector having an omnidirectional antenna or an antenna pointed in a particular direction radially away from the base station. Alternatively, each sector may include two or more different antennas. Each base station may be configured to support a plurality of frequency assignments, with each frequency assignment having a particular spectrum (e.g., 1.25 MHz, 5 MHz, etc.).

The intersection of sector and frequency assignment may be referred to as a CDMA channel. The base stations may also be referred to as Base Station Transceiver Subsystems (BTSs). In some cases, the term “base station” may be used to refer collectively to a BSC, and one or more base stations. The base stations may also be denoted as “cell sites.” Alternatively, individual sectors of a given base station may be referred to as cell sites.

A broadcasting transmitter (BT) transmits a broadcast signal to the mobile terminals 100 operating within the system. The broadcast receiving module 111 of FIG. 1A is typically configured inside the mobile terminal 100 to receive broadcast signals transmitted by the BT.

Global Positioning System (GPS) satellites for locating the position of the mobile terminal 100, for example, may cooperate with the CDMA wireless communication system. Useful position information may be obtained with greater or fewer satellites than two satellites. It is to be appreciated that other types of position detection technology, (i.e., location technology that may be used in addition to or instead of GPS location technology) may alternatively be implemented. If desired, at least one of the GPS satellites may alternatively or additionally be configured to provide satellite DMB transmissions.

The location information module 115 is generally configured to detect, calculate, or otherwise identify a position of the mobile terminal. As an example, the location information module 115 may include a Global Position System (GPS) module, a Wi-Fi module, or both. If desired, the location information module 115 may alternatively or additionally function with any of the other modules of the wireless communication unit 110 to obtain data related to the position of the mobile terminal.

A typical GPS module 115 can measure an accurate time and distance from three or more satellites, and accurately calculate a current location of the mobile terminal according to trigonometry based on the measured time and distances. A method of acquiring distance and time information from three satellites and performing error correction with a single satellite may be used. In particular, the GPS module may acquire an accurate time together with three-dimensional speed information as well as the location of the latitude, longitude and altitude values from the location information received from the satellites.

Furthermore, the GPS module can acquire speed information in real time to calculate a current position. Sometimes, accuracy of a measured position may be compromised if the mobile terminal is located in a blind spot of satellite signals, such as being located in an indoor space. In order to minimize the effect of such blind spots, an alternative or supplemental location technique, such as Wi-Fi Positioning System (WPS), may be utilized.

The Wi-Fi positioning system (WPS) refers to a location determination technology based on a wireless local area network (WLAN) using Wi-Fi as a technology for tracking the location of the mobile terminal 100. This technology typically includes the use of a Wi-Fi module in the mobile terminal 100 and a wireless access point for communicating with the Wi-Fi module.

The Wi-Fi positioning system may include a Wi-Fi location determination server, a mobile terminal, a wireless access point (AP) connected to the mobile terminal, and a database stored with wireless AP information.

The mobile terminal connected to the wireless AP may transmit a location information request message to the Wi-Fi location determination server. The Wi-Fi location determination server extracts the information of the wireless AP connected to the mobile terminal 100, based on the location information request message (or signal) of the mobile terminal 100. The information of the wireless AP may be transmitted to the Wi-Fi location determination server through the mobile terminal 100, or may be transmitted to the Wi-Fi location determination server from the wireless AP.

The information of the wireless AP extracted based on the location information request message of the mobile terminal 100 may include one or more of media access control (MAC) address, service set identification (SSID), received signal strength indicator (RSSI), reference signal received Power (RSRP), reference signal received quality (RSRQ), channel information, privacy, network type, signal strength, noise strength, and the like.

The Wi-Fi location determination server may receive the information of the wireless AP connected to the mobile terminal 100 as described above, and may extract wireless AP information corresponding to the wireless AP connected to the mobile terminal from the pre-established database. The information of any wireless APs stored in the database may be information such as MAC address, SSID, RSSI, channel information, privacy, network type, latitude and longitude coordinate, building at which the wireless AP is located, floor number, detailed indoor location information (GPS coordinate available), AP owner's address, phone number, and the like. In order to remove wireless APs provided using a mobile AP or an illegal MAC address during a location determining process, the Wi-Fi location determination server may extract only a predetermined number of wireless AP information in order of high RSSI.

Then, the Wi-Fi location determination server may extract (analyze) location information of the mobile terminal 100 using at least one wireless AP information extracted from the database.

A method for extracting (analyzing) location information of the mobile terminal 100 may include a Cell-ID method, a fingerprint method, a trigonometry method, a landmark method, and the like.

The Cell-ID method is used to determine a position of a wireless AP having the largest signal strength, among peripheral wireless AP information collected by a mobile terminal, as a position of the mobile terminal. The Cell-ID method is an implementation that is minimally complex, does not require additional costs, and location information can be rapidly acquired. However, in the Cell-ID method, the precision of positioning may fall below a desired threshold if the installation density of wireless APs is low.

The fingerprint method is used to collect signal strength information by selecting a reference position from a service area, and to track a position of a mobile terminal using the signal strength information transmitted from the mobile terminal based on the collected information. In order to use the fingerprint method, it is common for the characteristics of radio signals to be pre-stored in the form of a database.

The trigonometry method is used to calculate a position of a mobile terminal based on a distance between coordinates of at least three wireless APs and the mobile terminal. In order to measure the distance between the mobile terminal and the wireless APs, signal strength may be converted into distance information, Time of Arrival (ToA), Time Difference of Arrival (TDoA), Angle of Arrival (AoA), or the like may be taken for transmitted wireless signals.

The landmark method is used to measure a position of a mobile terminal using a known landmark transmitter.

In addition to these position location methods, various algorithms may be used to extract (analyze) location information of a mobile terminal. Such extracted location information may be transmitted to the mobile terminal 100 through the Wi-Fi location determination server, thereby acquiring location information of the mobile terminal 100.

The mobile terminal 100 can acquire location information by being connected to at least one wireless AP. The number of wireless APs required to acquire location information of the mobile terminal 100 may be variously changed according to a wireless communication environment within which the mobile terminal 100 is positioned.

As previously described with regard to FIG. 1A, the mobile terminal may be configured to include short-range communication techniques such as Bluetooth™, Radio Frequency Identification (RFID), Infrared Data Association (IrDA), UltraWideband (UWB), ZigBee, Near Field Communication (NFC), Wireless USB (Wireless Universal Serial Bus), and the like.

A typical NFC module provided at the mobile terminal supports short-range wireless communication, which is a non-contactable type of communication between mobile terminals and generally occurs within about 10 cm. The NFC module may operate in one of a card mode, a reader mode, or a P2P mode. The mobile terminal 100 may further include a security module for storing card information, in order to operate the NFC module in a card mode. The security module may be a physical medium such as Universal Integrated Circuit Card (UICC) (e.g., a Subscriber Identification Module (SIM) or Universal SIM (USIM)), a secure micro SD and a sticker, or a logical medium (e.g., embedded Secure Element (SE)) embedded in the mobile terminal. Single Wire Protocol (SWP)-based data exchange may be performed between the NFC module and the security module.

In a case where the NFC module operates in a card mode, the mobile terminal may transmit card information on a general IC card to the outside. More specifically, if a mobile terminal having card information on a payment card (e. g, a credit card or a bus card) approaches a card reader, a short-range mobile payment may be executed. As another example, if a mobile terminal which stores card information on an entrance card approaches an entrance card reader, an entrance approval procedure may start. A card such as a credit card, a traffic card, or an entrance card may be included in the security module in the form of applet, and the security module may store card information on the card mounted therein. Card information for a payment card may include any of a card number, a remaining amount and usage history, and the like. Card information of an entrance card may include any of a user's name, a user's number (e.g., undergraduate number or staff number), an entrance history, and the like.

If the NFC module operates in a reader mode, the mobile terminal can read data from an external tag. The data received from the external tag by the mobile terminal may be coded into the NFC Data Exchange Format defined by the NFC Forum. The NFC Forum generally defines four record types. More specifically, the NFC Forum defines four Record Type Definitions (RTDs) such as smart poster, text, Uniform Resource Identifier (URI), and general control. If the data received from the external tag is a smart poster type, the controller may execute a browser (e.g., Internet browser). If the data received from the external tag is a text type, the controller may execute a text viewer. If the data received from the external tag is a URI type, the controller may execute a browser or originate a call. If the data received from the external tag is a general control type, the controller may execute a proper operation according to control content.

In some cases in which the NFC module operates in a P2P (Peer-to-Peer) mode, the mobile terminal can execute P2P communication with another mobile terminal. In this case, Logical Link Control Protocol (LLCP) may be applied to the P2P communication. For P2P communication, connection may be generated between the mobile terminal and another mobile terminal. This connection may be categorized as a connectionless mode which ends after one packet is switched, and a connection-oriented mode in which packets are switched consecutively. For a typical P2P communication, data such as an electronic type name card, address information, a digital photo and a URL, a setup parameter for Bluetooth connection, Wi-Fi connection, etc. may be switched. The P2P mode can be effectively utilized in switching data of a small capacity, because an available distance for NFC communication is relatively short.

Further preferred embodiments will be described in more detail with reference to additional drawing figures. It is understood by those skilled in the art that the present features can be embodied in several forms without departing from the characteristics thereof.

FIG. 5 is a ladder diagram illustrating an operating method between a mobile terminal 100 and a peripheral device 500, according to an embodiment of the present disclosure.

In the following drawings, the peripheral device 500 may be a device capable of interworking with the mobile terminal 100. Specifically, the peripheral device 500 and the mobile terminal 100 may be wiredly or wirelessly connected to each other.

The peripheral device 500 may be a device which is attachable to and detachable from the mobile terminal 100 in a module type.

The peripheral device 500 may be at least one of a camcorder, a Bluetooth headset, an earphone, an omnidirectional capturing device capturing an image of an omnidirectional region, a virtual reality display device, a portable digital-analog converter, a home monitoring camera, and a drone, but theses are mere examples.

Referring to FIG. 5, the controller 180 of the mobile terminal 100 acquires an image of the peripheral device 500 through a camera 121 (S501).

In an embodiment, the controller 180 may execute an application providing a service which is capable of controlling an operation of the peripheral device 500.

If a search button for searching for the peripheral device 500 is selected on a screen of the executed application, the controller 180 may turn on power of the camera 121 and display an image acquired through the camera 121 on a display unit 151.

The image acquired through the camera 121 may be a preview image. The preview image may be an image in which the image acquired through the camera 121 is displayed on the display unit 151 in real time.

The controller 180 of the mobile terminal 100 identifies the peripheral device 500 based on the acquired image of the peripheral device 500 (S503).

In an embodiment, the controller 180 may identify the peripheral device 500 based on a marker included in the image of the peripheral device 500 and attached to the peripheral device 500.

The marker attached to the peripheral device 500 may include information for identifying the peripheral device 500. For example, the marker attached to the peripheral device 500 may include at least one of a name, a model name, and a version of the peripheral device 500, and link information for providing information on the peripheral device 500.

The link information may be a website access address capable of providing the information on the peripheral device 500.

In another embodiment, the controller 180 may identify the peripheral device 500 based on a shape of the peripheral device 500.

The controller 180 may recognize the shape of the peripheral device 500 through the image of the peripheral device 500, which is displayed on the display unit 151.

The peripheral device 500 may have various shapes according to a model or a version thereof. For example, a memory 170 of the mobile terminal 100 may store three-dimensional (3D) modeling information according to a model name of a specific product.

The memory 170 may store identification information on the peripheral device 500 and 3D modeling information corresponding to the identification information.

The 3D modeling information may include various 3D shapes in which the peripheral device 500 is capable of being disposed in a virtual 3D space. The various 3D shapes may be 3D modeling samples modeled in the 3D virtual space, respectively.

The controller 180 may compare the shape of the peripheral device 500 with the 3D modeling information, the shape of the peripheral device 500 being included in the image of the peripheral device 500, which is acquired through the camera 121. If the shape of the peripheral device 500 matches a 3D modeling shape, the controller 180 may acquire the identification information on the peripheral device 500.

Meanwhile, the memory 170 may prestore the identification information on the peripheral device 500 and the 3D modeling information corresponding to the identification information, but the present disclosure is not limited thereto. That is, the controller 180 may transmit the image of the peripheral device 500 to an external server. The external server may store the identification information on the peripheral device 500 and the 3D modeling information corresponding to the identification information.

The external server may perform the aforementioned comparing process through the image of the peripheral device 500 received through the mobile terminal 100, and thus, acquire the identification information on the peripheral device 500. The external server may transmit the acquired identification information on the peripheral device 500 to the mobile terminal 100. Therefore, the mobile terminal 100 may acquire the identification information on the peripheral device 500.

On the other hand, the controller 180 may also recognize the peripheral device 500 based on the shape and a color of the peripheral device 500.

In another embodiment, the controller 180 may identify the peripheral device 500 based on the marker attached to the peripheral device 500 and the shape of the peripheral device 500.

That is, the controller 180 may acquire second identification information on the peripheral device 500 based on first information on the peripheral device 500 acquired through the marker of the peripheral device 500 and the shape of the peripheral device 500.

If the first information matches the second information, the controller 180 may determine that the peripheral device 500 is identified. Therefore, the mobile terminal 100 may more accurately identify the peripheral device 500 without an error.

If the first information does not match the second information, the controller 180 may perform an identification process again.

In another embodiment, if the peripheral device 500 is not identified based on the marker attached to the peripheral device 500, the controller 180 may identify the peripheral device 500 based on the shape of the peripheral device 500.

The case where the peripheral device 500 is not identified based on the marker attached to the peripheral device 500 may mean a case where the identification information on the peripheral device 500 is not acquired. The marker attached to the peripheral device 500 has no choice but to have a small size due to restriction on an exterior design.

In addition, an angle for photographing the peripheral device 500 may be changed according to users. Even if the peripheral device 500 is photographed, the marker attached to the peripheral device 500 may not be properly photographed. Accordingly, the mobile terminal 100 may not identify the peripheral device 500.

First, the controller 180 may determine whether the identification information on the peripheral device 500 is acquired based on the marker attached to the peripheral device 500. If the identification information on the peripheral device 500 is not acquired, the controller 180 may acquire the identification information on the peripheral device 500 through a comparison between the shape of the peripheral device 500 and the 3D modeling information on the peripheral device 500.

Therefore, even if the peripheral device 500 is not identified through the marker attached to the peripheral device 500, the peripheral device 500 may be identified through the shape of the peripheral device 500. That is, the identification of the peripheral device 500 may be complemented through the shape of the peripheral device 500.

In an embodiment, the marker attached to the peripheral device 500 may include at least one of a quick response (QR) code and a barcode, which contain information on the peripheral device 500 in a digital form, but theses are mere examples.

The marker attached to the peripheral device 500 may have an icon shape, but this is a mere example.

The controller 180 displays connection guide information for a connection with the identified peripheral device 500 on the display unit 151 (S505).

In an embodiment, the connection guide information may be information including a guide which is capable of rapidly performing pairing with the identified peripheral device 500.

The connection guide information may further include information on a communication standard for the communication with the identified peripheral device 500.

In an embodiment, the controller 180 may display the connection guide information in an augmented reality.

The connection guide information may be displayed so as to overlap the image of the peripheral device 500 displayed on the display unit 151.

The controller 180 of the mobile terminal 100 is paired with the peripheral device 500 according to a selection of the connection guide information (S507).

If the connection guide information is selected, the controller 180 may transmit a connection request to the peripheral device 500 through a short-range communication module 114 and receive a connection response from the peripheral device 500.

Therefore, the mobile terminal 100 and the peripheral device 500 are paired with each other and exchange information therebetween.

In another embodiment, the display of the connection guide information may be omitted. In this case, if the peripheral device 500 is identified, the mobile terminal 100 may be automatically paired with the identified peripheral device 500.

Operations S501 and S507 will be described with reference to the following drawings.

FIGS. 6A and 6B are diagrams illustrating a process of capturing an image of the peripheral device 500 and performing paring with the peripheral device 500, according to an embodiment of the present disclosure.

Referring to FIG. 6A, the mobile terminal 100 displays an execution screen 610 of an application providing a service for controlling an operation of the peripheral device 500. The application may provide information for controlling the operation of the peripheral device 500 in an augmented reality.

The execution screen 610 of the application may include a search button 611 for a connection with the peripheral device 500.

If the search button 611 is selected, the controller 180 may display information 610 on a peripheral device on the execution screen 610, the peripheral device being pairable with the mobile terminal 100.

The execution screen 610 may further include information 613 on a peripheral device previously paired with the mobile terminal 100.

On the other hand, if the peripheral device pairable with the mobile terminal 100 is searched for, as shown in FIG. 6A, the controller 180 may display scanning guide information 620 for scanning an identification tag attached to the peripheral device 500. The identification tag may be an example of a marker.

The scanning guide information 620 may further information a text indicating “start paring with the peripheral device 500”.

The scanning guide information 620 may be displayed if an image 630 of a peripheral device is focused at the time of capturing.

The mobile terminal 100 may display the image 630 of the peripheral device acquired through a camera (not shown) while displaying the scanning guide information 620. That is, the mobile terminal 100 may display the scanning guide information 620 while displaying a preview image.

Thereafter, the controller 180 of the mobile terminal 100 may identify the peripheral device 500 based on a marker image 631 included in the image 630 of the peripheral device. That is, a marker 501 containing identification information on the peripheral device 500 may be attached to the peripheral device 500.

As illustrated in FIG. 5, the controller 180 may identify the peripheral device 500 based on the marker 501.

If the peripheral device 500 is identified, as shown in FIG. 6B, the controller 180 may display connection guide information 633 for a connection with the identified peripheral device 500.

In order to perform short-range wireless communication with the identified peripheral device 500, the connection guide information 633 may include guide information for selecting the connection guide information 633.

If the connection guide information 633 is selected, the controller 180 may be paired with the peripheral device 500 through the short-range communication module 114.

FIG. 5 will be described again.

The controller 180 of the mobile terminal 100 receives information on the paired peripheral device 500 through the short-range communication module 114 (S509).

In an embodiment, the information on the paired peripheral device 500 may be any one of information on content stored in the peripheral device 500, an image provided in streaming by the peripheral device 500, and identification information on the peripheral device 500.

The content stored in the peripheral device 500 may be any one of a video and an image, but theses are mere examples.

The controller 180 of the mobile terminal 100 displays one or more menu items based on the received information on the peripheral device 500 (S511).

In an embodiment, each of the one or more menu items may be an item for providing the information on the paired peripheral device 500.

For example, each of the one or more menu items may be an identification item for providing identification information on the paired peripheral device 500.

In another example, each of the one or more menu items may be a battery item for providing battery information on the paired peripheral device 500.

In another example, each of the one or more menu items may be a memory item for providing memory information on the paired peripheral device 500.

In another example, each of the one or more menu items may be a wireless communication item for providing wireless communication connection status information on the paired peripheral device 500.

In another example, each of the one or more menu items may be a content item for providing content stored in the paired peripheral device 500. The content may be at least one of a video file, a photo file, and an audio file, but theses are mere examples.

In another example, each of the one or more menu items may be a streaming item for providing an image captured in real time by the paired peripheral device 500.

The one or more menu items have been described as examples, but attributes of the one or more menu items may be changed according to a type of the paired peripheral device 500. That is, a menu item corresponding to the type of the paired peripheral device 500 may be provided according to the type of the paired peripheral device 500.

The controller 180 of the mobile terminal 100 provides information on the peripheral device 500, which corresponds to a menu item selected from the one or more menu items (S513).

The controller 180 may display the information on the peripheral device 500 such that the information corresponding to the menu item selected from the one or more menu items overlaps an image of the peripheral device 500. The controller 180 may provide the information on the paired peripheral device 500 in an augmented reality, the information corresponding to the selected menu item.

Hereinafter, operations S511 and S513 will be described in detail.

FIGS. 7 to 8 are diagrams illustrating a process of providing information on the peripheral device 500 paired with the mobile terminal 100, according to an embodiment of the present disclosure.

In FIGS. 7 and 8, the mobile terminal 100 displays an image of an image 630 of a peripheral device acquired through the camera 121.

Referring to FIG. 7, after the mobile terminal 100 is paired with the peripheral device 500, the controller 180 may display a menu list 700 for providing information on the peripheral device 500 on the display unit 151.

The menu list 700 may be displayed so as to overlap the image 630 of the peripheral device. The menu list 700 may be provided in an augmented reality.

The menu list 700 may include one or more menu items.

The menu list 700 may include an identification item 710, a battery item 720, a memory item 730, a wireless communication item 740, and a content item 750.

The identification item 710 may be an item for providing identification information identifying the paired peripheral device 500. The identification information may include a model name, a version, a name, and a usage of the peripheral device 500.

If the identification item 710 is selected, the controller 180 may display the identification information on the peripheral device 500 on the display unit 151.

The battery item 720 may be an item for providing identification on a residual amount of a battery mounted in the paired peripheral device 500.

The memory item 730 may be an item for providing a current residual capacity with respect to a total capacity of a memory provided in the peripheral device 500.

The wireless communication item 740 may be an item for providing whether a short-range module provided in the peripheral device 500 is connected through a specific wireless standard.

The content item 750 may be an item for providing information on content stored in the peripheral device 500.

For example, as shown in FIG. 7, if the content item 750 is selected, the controller 180 may display a plurality of images 751 to 755 stored in the peripheral device 500.

A user may rapidly view the content stored in the peripheral device 500 without wiredly connecting the peripheral device 500 to the mobile terminal 100.

In an embodiment, each of the plurality of images 751 to 755 may be an image most recently stored in the peripheral device 500. A first image 751 may be the image most recently stored in the peripheral device 500 and a second image 753 and a third image 755 may be sequentially stored after the first image 751.

If the content item 750 is selected, a plurality of type menus may be further displayed according to a content type. For example, the plurality of type menus may include a video menu, a photo menu, and an audio menu.

If any one of the plurality of type menus is selected, the controller 180 may display content corresponding to a selected type menu. For example, if the photo menu is selected, the controller 180 may display only photos of content stored in the peripheral device 500.

According to another embodiment of the present disclosure, one or more menu items may be disposed around the marker image 631 included in the image 630 of the peripheral device.

Referring to FIG. 8, a plurality of menu items 760 to 780 may be disposed around the marker image 631.

A view menu item 760 may be an item for displaying content stored in the peripheral device 500 and may be the same as the content item 750 of FIG. 7.

A mode menu item 770 may be an item for controlling an operation mode of the peripheral device 500. The peripheral device 500 may operate in any one of a plurality of operation modes according to a type thereof. The mode menu item 770 may be an item for providing the plurality of operation modes with respect to the peripheral device 500.

An info item 780 may be an item for providing identification information on the peripheral device 500 and may be the same as the identification item 710 of FIG. 7.

If the view menu item 760 is selected, as shown in FIG. 8, the controller 180 may display a plurality of images 751 to 755 stored in the peripheral device 500.

The plurality of menu items 760 to 780 disposed around the marker image 631 may be displayed based on information included in the marker 501 itself of the peripheral device 500.

On the contrary, each of the plurality of menu items 710 to 750 shown in FIG. 7 may be an item generated based on information received from the peripheral device 500 itself.

On the other hand, according to another embodiment of the present disclosure, a size of content to be displayed may be changed according to a distance between the mobile terminal 100 and the peripheral device 500.

FIG. 9 is a diagram illustrating an example of a change in a size of content stored in the peripheral device 500 paired with the mobile terminal 100 according to a distance between the peripheral device 500 and the mobile terminal 100, according to an embodiment of the present disclosure.

In FIG. 9, the mobile terminal 100 displays an image 630 of a peripheral device acquired through the camera 121.

Referring to FIG. 9, the mobile terminal 100 displays a plurality of images 751 to 755 stored in the paired peripheral device 500 through the display unit 151.

In this state, if the mobile terminal 100 moves closer to the peripheral device 500, the controller 180 may increase a size of each of the plurality of images 751 to 755. That is, the plurality of images 751 to 755 may each be enlarged and displayed.

The phrase “the mobile terminal 100 moves closer to the peripheral device 500” may mean that there exists a user's intension to more closely view content.

If it is sensed that the mobile terminal 100 moves closer to the peripheral device 500, the mobile terminal 100 may enlarge and display each of the plurality of images 751 to 755 by reflecting the user's intention.

In an embodiment, the controller 180 may sense through a distance sensor provided in the mobile terminal 100 that the mobile terminal 100 moves closer to the peripheral device 500. The controller 180 may determine based on a sensing result whether the mobile terminal 100 moves away from or closer to the peripheral device 500.

In another embodiment, the controller 180 may determine whether the mobile terminal 100 moves closer to the peripheral device 500, based on the image 630 of the peripheral device displayed on the display unit 151.

If the image 630 of the peripheral device 500 becomes larger, the controller 180 may determine that the mobile terminal 100 moves closer to the peripheral device 500.

The user may closely view content stored in the peripheral device 500 only through an operation of moving the mobile terminal 100 toward the peripheral device 500 without a complicated process.

Next, a method of displaying content enlarged as the mobile terminal 100 moves closer to the peripheral device 500 will be described.

In an embodiment, if it is sensed that the mobile terminal 100 moves closer to the peripheral device 500, the controller 180 may enlarge an image itself displayed on the display unit 151. That is, a main agent enlarging an image is the mobile terminal 100.

In another embodiment, if it is sensed that the mobile terminal 100 moves closer to the peripheral device 500, the controller 180 may receive an enlarged image from the peripheral device 500. That is, a main agent enlarging an image is the peripheral device 500.

If it is sensed that the mobile terminal 100 moves closer to the peripheral device 500, the controller 180 may transmit a request for image enlargement to the peripheral device 500, and the peripheral device 500 may output an enlarged image in response to the request for the image enlargement. The controller 180 may receive the enlarged image output from the peripheral device 500 and display the enlarged image on the display unit 151.

On the other hand, if displayed content is selected, the controller 180 may store the selected content in the memory 170 of the mobile terminal 100.

FIG. 10 is a diagram illustrating an example in which content stored in the peripheral device 500 displayed on the mobile terminal 100 is stored in the mobile terminal 100 if the content is selected, according to an embodiment of the present disclosure.

Referring to FIG. 10, if a first image 751 of a plurality of images 751 to 755 is selected, the controller 180 may store the selected first image 751 in the memory 170. The first image 171 may be stored in the memory 170 together with identification information on the peripheral device 500 providing the first image 751.

The controller 180 may display the stored first image 751 on an execution screen 1000 of a gallery application. The controller 180 may display source information and the first image 751 on the execution screen 1000 of the gallery application by using the identification information on the peripheral device 500, the source information being used for identifying who a provider of the first image 751 is.

The user may rapidly download the content stored in the peripheral device 500 to the mobile terminal 100 without a complicated process.

FIG. 11 is a diagram illustrating a process of controlling an operation of the peripheral device 500 paired with the mobile terminal 100, according to an embodiment of the present disclosure.

Descriptions in FIG. 11 assume that the peripheral device 500 is an action cam having a function for transmitting a captured image to other devices in real time.

In addition, descriptions in FIG. 11 assume that the mobile terminal 100 is paired with the action cam and an image 1100 of the action cam is displayed on the display unit 151.

Referring to FIG. 11, the camera 121 provided in the mobile terminal 100 is turned on, an augmented reality icon 1101 may be displayed on a preview screen, the augmented reality icon 1101 indicating that the mobile terminal 100 is operable in an augmented reality mode.

If the augmented reality icon 1101 is selected, the controller 180 may display a menu list 700 for providing information on the action cam so as to overlap the image 1100 of the action cam.

The menu list 700 may include a streaming icon 1110 for providing a real-time image acquired by the action cam.

If the streaming icon 1110 is selected, the controller 180 may display a real-time image 1130 acquired by the action cam through the display unit 151. At this time, the image 1100 of the action cam may disappear.

If the streaming icon 1110 is selected, the controller 180 may request the action cam to transmit the real-time image 1130 and may receive the real-time image 1130 as a response to the request. The controller 180 may display the received real-time image 1130.

The action cam may be mounted on a user's helmet at the time of exercising or driving, and the user may promptly confirm an image captured through the action cam.

According to an embodiment of the present disclosure, even if the action cam is mounted on the user's helmet, the user may exercise or drive while easily viewing the image captured in real time through the action cam.

In addition, since a pairing process between the mobile terminal 100 and the action cam is simplified, the user may rapidly connect the action cam to the mobile terminal 100.

FIGS. 12 and 13 are diagrams illustrating an example in which the mobile terminal 100 captures an image of the peripheral device 500, is paired with the peripheral device 500, and provides information on the peripheral device 500 in an augmented reality, according to another embodiment of the present disclosure.

In FIGS. 12 and 13, the peripheral device 500 may be a Bluetooth earphone outputting an audio.

Referring to FIG. 12, the controller 180 may display scanning guide information 1230 overlapping an image 1210 of a peripheral device acquired through the camera 121.

The contents of the scanning guide information 1230 may be the same as the contents of the scanning guide information 620 described with reference to FIG. 6A.

If the image 1210 of the Bluetooth earphone is identified, the mobile terminal 100 may be paired with the Bluetooth earphone.

Thereafter, the controller 180 may display a menu list 1250 for providing information on the Bluetooth earphone on the display unit 151.

The menu list 1250 may include a status check item 1251, a voice memo item 1253, and a music list item 1255.

The status check item 1251 may be an item for checking a status of the Bluetooth earphone. The status of the Bluetooth earphone may include at least one of a battery status, a wireless communication connection status, and a memory status of the Bluetooth earphone.

The voice memo item 1253 may be an item for outputting voice memos stored in the Bluetooth earphone as an audio.

The music list item 1255 may be an item for providing playable music.

If the voice memo item 1253 is selected, as shown in FIG. 13, the controller 180 may display a voice memo list 1300.

If a specific voice memo 1310 included in the voice memo list 1300 is selected, the controller 180 may output an audio corresponding to the selected specific voice memo 1310 through an audio output module 152 provided in the mobile terminal 100. An audio corresponding to a voice memo may be an audio in which a user's voice is recorded.

The controller 180 may receive the audio corresponding to the selected specific voice memo 1310 from the Bluetooth earphone and output the received audio through the audio output module 152.

The user may rapidly listen to a voice memo recorded through the Bluetooth earphone only though an operation of photographing the Bluetooth earphone.

On the other hand, if it is sensed that the mobile terminal 100 moves closer to the Bluetooth earphone, the controller 180 may display a text 1330 corresponding to the specific voice memo 1310 output as the audio on the display unit 151.

That is, referring to FIG. 13, if it is sensed that the mobile terminal 100 moves closer to the Bluetooth earphone, the controller 180 may display the text 1330 corresponding to the selected specific voice memo 1310. Of course, the audio corresponding to the specific voice memo 1310 is in a state of being output through the audio output module 152.

The user may confirm the voice memo 1310 as a text only through an operation of moving the mobile terminal 100 closer to the Bluetooth earphone while listening to the audio corresponding to the specific voice memo 1310.

According to another embodiment of the present disclosure, it is possible to identify a version of the peripheral device 500 and provide information on the peripheral device 500 corresponding to the identified version.

FIG. 14 is a diagram illustrating an example in which a version of the peripheral device 500 is recognized and information on the peripheral device 500 corresponding to the recognized version is provided, according to an embodiment of the present disclosure.

FIG. 14 illustrates that the mobile terminal 100 is paired with the peripheral device 500 and guide information for controlling an operation of the peripheral device 500 is displayed. In FIG. 14, it is assumed that an image 630 of the peripheral device 500 captured through the camera 121 of the mobile terminal 100 is continuously displayed on the display unit 151.

The guide information may include a guide to a function of a button provided in the peripheral device 500.

Even if a plurality of peripheral devices 500 are the same model, the plurality of peripheral devices 500 may differ in a function or an operation according to a version of a product.

The mobile terminal 100 may acquire a model of the peripheral device 500 by capturing the image 630 of the peripheral device at the time of identifying the peripheral device 500.

The mobile terminal 100 may additionally acquire a version corresponding to the model of the peripheral device 500. Version information on the peripheral device 500 may be included in a marker of the peripheral device 500, but is not limited thereto.

That is, the version information on the peripheral device 500 may be attached to the peripheral device 500 independently from the marker. In this case, the mobile terminal 100 may recognize the version of the peripheral device 500 by recognizing a version tag attached independently from the marker.

The mobile terminal 100 may provide information corresponding to the recognized version of the peripheral device 500.

For example, if the version of the peripheral device 500 is version 1.1, the controller 180 may provide information on the peripheral device 500 corresponding to version 1.1. If the version of the peripheral device 500 is version 1.2, the controller 180 may provide information on the peripheral device 500 corresponding to version 1.2.

The controller 180 may display a website screen providing information on the peripheral device 500 corresponding to a relevant version. In this case, the version tag may further include link information for providing the website screen.

Even if peripheral devices are the same model, the user may receive information on peripheral devices having different versions.

Therefore, the user may receive accurate information corresponding to a relevant version.

The present disclosure mentioned in the foregoing description may be implemented using a machine-readable medium having instructions stored thereon for execution by a processor to perform various methods presented herein. Examples of possible machine-readable mediums include HDD (Hard Disk Drive), SSD (Solid State Disk), SDD (Silicon Disk Drive), ROM, RAM, CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, the other types of storage mediums presented herein, and combinations thereof. If desired, the machine-readable medium may be realized in the form of a carrier wave (for example, a transmission over the Internet). The processor may include the controller 180 of the mobile terminal.

The foregoing embodiments are merely exemplary and are not to be considered as limiting the present disclosure. This description is intended to be illustrative, and not to limit the scope of the claims. Many alternatives, modifications, and variations will be apparent to those skilled in the art. The features, structures, methods, and other characteristics of the exemplary embodiments described herein may be combined in various ways to obtain additional and/or alternative exemplary embodiments.

As the present features may be embodied in several forms without departing from the characteristics thereof, it should also be understood that the above-described embodiments are not limited by any of the details of the foregoing description, unless otherwise specified, but rather should be considered broadly within its scope as defined in the appended claims, and therefore all changes and modifications that fall within the metes and bounds of the claims, or equivalents of such metes and bounds, are therefore intended to be embraced by the appended claims. 

What is claimed is:
 1. A mobile terminal comprising: a display; a camera configured to acquire an image of a peripheral device; a hardware communication module configured to perform wireless communication with the peripheral device; and a hardware controller configured to: identify the peripheral device based on at least a marker included in the acquired image or a shape of the peripheral device obtained via the acquired image, and pair the mobile terminal with the identified peripheral device via the communication module, and control the display to display the image of the paired peripheral device and information on the paired peripheral device wherein the controller is further configured to control the display to display one or more menu items for providing information on the peripheral device, and wherein an attribute of each of the one or more menu items is changed according to a type of the peripheral device.
 2. The mobile terminal of claim 1, wherein the controller is further configured to identify the peripheral device by using the shape of the peripheral device if the peripheral device is not identified based on the marker.
 3. The mobile terminal of claim 2, further comprising a memory configured to store three-dimensional (3D) modeling information on the peripheral device, wherein the controller is further configured to identify the peripheral device using a comparison between the shape of the peripheral device and the 3D modeling information stored in the memory.
 4. The mobile terminal of claim 1, wherein the mobile terminal is automatically paired with the peripheral device if the peripheral device is identified.
 5. The mobile terminal of claim 1, wherein the controller is further configured to control the display to display information comprising a connection guide for pairing with the peripheral device on the display unit if the peripheral device is identified.
 6. The mobile terminal of claim 1, wherein the controller is further configured to control the display to display a plurality of contents stored at the peripheral device if a menu item for providing content stored at the peripheral device is selected among the one or more menu items.
 7. The mobile terminal of claim 6, wherein the controller is further configured to control the display to display the plurality of contents in an enlarged size if it is sensed that the mobile terminal is moved closer to the peripheral device.
 8. The mobile terminal of claim 7, wherein the plurality of contents are displayed in the enlarged size when: a signal for displaying the plurality of contents in the enlarged size is received from the peripheral device via the communication module; or the controller enlarges the size of the displayed plurality of contents.
 9. The mobile terminal of claim 6, wherein the controller is further configured to download a content of the plurality of displayed contents in response to a selection of the content.
 10. A mobile terminal comprising: a display; a camera configured to capture an image of a peripheral device; a hardware communication module configured to perform wireless communication with the peripheral device; and a hardware controller configured to: identify the peripheral device based on a shape of the peripheral device obtained via the acquired image; perform pairing with the identified peripheral device via the communication module; and control the display to display the image of the peripheral device and information on the peripheral device, wherein the controller is further configured to control the display to display one or more menu items for providing the information on the peripheral device, and wherein an attribute of each of the one or more menu items is changed according to a type of the peripheral device.
 11. The mobile terminal of claim 10, further comprising a memory configured to store 3D modeling information on the peripheral device, wherein the controller is further configured to identify the peripheral device using a comparison between the shape of the peripheral device and the 3D modeling information stored in the memory.
 12. The mobile terminal of claim 10, wherein the controller is further configured to control the display to display information comprising connection guide information for pairing with the peripheral device if the peripheral device is identified.
 13. The mobile terminal of claim 10, wherein the controller is further configured to control the display to display a plurality of contents stored at the peripheral device if a menu item for providing content stored at the peripheral device is selected among the one or more menu items.
 14. The mobile terminal of claim 13, wherein the controller is further configured to control the display to display the plurality of contents in an enlarged size if it is sensed that the mobile terminal is moved closer to the peripheral device.
 15. The mobile terminal of claim 14, wherein the plurality of contents are displayed in the enlarged size when: a signal for displaying the plurality of contents in the enlarged size is received from the peripheral device via the communication module; or the controller enlarges the size of the displayed plurality of contents.
 16. The mobile terminal of claim 13, wherein the controller is further configured to download a content of the plurality of displayed contents in response to a selection of the content.
 17. The mobile terminal of claim 10, wherein the one or more menu items comprises: a battery menu item for providing battery information of the peripheral device; a memory menu item for providing memory information of the peripheral device; and a wireless communication menu item for providing wireless communication connection status information of the peripheral device. 